Labels:text | screenshot | black and white OCR: The MEDUtils package consists of EDPlay, MEDRip, MEDAlloc and MEDWipe which were written by Ben Hutchings and released in September 1994 The contents of this package are the files: InstallBB, InstallBBUB, InstallBBWB. info, MEDAlloc, MEDAlloc. BB, MEDAlloc. info, MEDPlay, MEDPlay. info, MEDRip, MEDRip. info, MEDUtils.doc, MEDUtils.doc. info, MEDWipe, MEDWipe. info. These files are all copyright (c) Ben Hutchings 1994, but (i) they may be freely distributed provided no charge is made for them above the costs of duplication, distribution and the media used, (ii) all the listed files are kept together, and (iii) the files are unaltered. The exception to (iii) is that the files may be distributed in a compressed form as long as the original files can be retrieved from this form unchanged. Software released under these conditions is often known as Freeware. The files medplayer. library and octaplayer. library are also he files med part of the package. However the copyrights to these belong to Tel jo Kinnunen. The file reqtools. library is copyrighted by Nico Frantois. These files can copied separately, but they are intended to be included as part of this package. I reject any responsibility for any undesirable consequences whatever of the use of this software. This includes, but is not limited to, secondary consequences, personal injuries or other kinds of side effects. usefulre inadequate and out-dated. I hope you Find them as ocumentre fani idual programs: The limitation of ripping is this: unless you have an Action Replay cartridge, you can't actually stop the game while its running and rip out data without disturbing anything. Nevertheless, I have found this ripper software to be very effective. So there's your quick guide to modules. Read on to find out how to use the programs in this package. Please note that as yet none of the programs are capable of handling the newest 'MMD2' module type which OctaMED 5 can produce. However this doesn't seem to be common yet. ained later on for temporary use only),“ Metal another disk, you must simply drag their Workbench icon to the other disk. MEDPlay and MEDPlay13, however, need several library files to accompany them. I will explain how to install these in moment. They both require 'reqtools. library' , and MEDPlay13 also requires 'medplayer. library' . If you will use MEDPlay13 to play 8-channel modules you will also need octaplayer. library' . To install all the libraries you need, do this: Boot from your hard disk. Open a Shell/CLI. Enter 'List LIBS:'. A list of libraries already installed will appear. Any library you need that is ON THAT LIST will NOT need to be installed. Insert the disk this text is on. Change the current directory to the directory this text is in - you will have to type something like 'CD DPO : MEDUtils'. For each library you need to install, type 'Copy to LIBS:' followed by a space and the name of the library, then press Return. Enter 'EndCLI' to close the Shell/CLI. You can then drag the MEDPlay or MEDPlay13 icon to wherever you want it on your hard disk, and it should run from there. HEDPLAY version because including the code seemed to me a waste 11ssing the pace considering the rarity of 8-channel modules. You c still use MEDPlay13 under OS 2.0 if you want but without some of the benefits of the special 2.0 version. Except where noted, the information below applies to bot versions of the program. One of the reasons I had for writing this was for use in disk magazines (I was hoping to produce one myself but that will have to wait). Although it can be run from Workbench, MEDPlay is designed for control by Shell commands and especially by scripts. Shell usage: To start playing a module, or to change the music already playing, type MEDPlay <module_name> or MEDPlay <module_name> LOOP where <module_name> represents the name of the module, a LOOP is an optional switch which disables the anti-loopi feature of MEDPlay. o use a file requester to start/stop music, just type MEDPlay then pick a module or click Cancel to stop. The requester will keep coming back when each piece of music finishes, until you click Cancel. If you are using the 2.0 version of MEDPlay you can specify multiple modules on the command line or in the file request- er (using Shift-select). The 2.0 version will also play all the songs in a multi-module one after another. In the 2.0 version you can also stop a single song by pressing Ctrl-C, or you can completely exit the program by pressing Ctrl-D. If MEDPlay is running in the background you can use the Break command to do this (see your Commodore hanual for information about this). NOTE: If you use MEDPlay in a script for a disk magazine or similar, you will need to run MEDPlay in 'background' with the Run command. If you want to put something 11ke MEDPlay intro.mod in a startup-sequence, e.g. Echo "Welcome to XYZ disk magazine issue #51" MEDPlay intro.mod LoadUB EndCLI >NIL: you will actually need to use the command Rum >MIL: < MIL: MEDPlay >NIL: < MIL: intro.mod otherwise the Shell window will just stay on the screen and do nothing until the music finishes. If MEDPlay is asked to STOP and there isn't actually any music playing, it will return code 5 (WARM) in case you want your script to check for this. Obviously if something else goes wrong it will return code 20 (FAIL) which will terminate your script unless you use the Failat command (see your Commodore manual for details) to prevent this. Workbench usage: If you are using the OS 2.0 version, there are three poss- ible ways to start MEDPlay from the Workbench. . If your modules are saved with icons, you can set their default tool (using the Workbench 'Information' function) to something like 'SYS:utilities/MEDPlay' (assuming that you have installed MEDPlay in the 'utilities' drawer of your hard disk). Then, when you double-click then they will be played using MEDPlay. If your modules have icons, you can use extended selection to play them. What this means is, select the first one, then hold down Shift and select any others, then (keeping Shift held down) double-click MEDPlay's 3. Double-click on the MEDPlay or MEDPlay13 icon. A file icon. requester will appear. Select the drawer your modules are stored in. Then select a module and click OK. In the 2.0 version you can select as many modules as you want using Shift-selection. The 2.0 version will also go through multi-modules playing all the modules, whereas the 1.3 version will not. The requester will re-appear when the module(s) stop. You can then stop by clicking Cancel or select a module or modules again to go on playing. MEDPlay. Method 3 is the only one which works with the 1.3 version of You can stop a module which is already playing before it ends by starting MEDPlay from its icon and clicking Cancel. HEDRIP spory within the Completely ton of this docu mes which" nadused on i the use of ripper programs of any kind no certainly do so. Refer to your license agreement if Shell usage: To begin searching for modules, type MEDRip and wait. When a module is found, brief information about it will be displayed in the window - including some kind of name. To save the module, type in a filename - e.g. DFO : NiceRay TracedDenoTune - and press Return. To skip it, just press Return. When the search When the search is finished, a Shell prompt will reappear. Workbench usage: Double-click the MEDRip icon. When a module is found, brief information about it will be displayed in a window, probably including some kind of nan or other identification. To save the module, type in a filename - e.g. DFO:MiceRay TracedDenoTune - and press Return. To skip it, just press Return. When the search is finished, the window will disappear. This program installs a special 'KickTag' which is run immediately after any reset. The KickTag code will find any (Octa)MED modules in memory and allocate the memory they use so that they are protected from being written wuer. This means that you can rip many modules which you aight otherwise not be able to. To run it, simply double-click the MEDAlloc icon or run EDAlloc from the Shell. A message will appear telling you to reboot when ready. This means that you can nou auscami the screen vi ich longer than ost Can then Pun MEDRip to rip the nodu les "described onger Be Found and will not operate when you reset" in this Case you Can use a slightly less effective method" I have included a special bootblock which you can put on a floppy disk along with the MEDRip program which does the same thing as the MEDAlloc 'KickTag' code. Format a standard disk (not a high-density one) then put this disk in and double-click the InstallBBWB icon. You will be asked to insert a disk to be installed. Insert the formatted disk in the INTERMAL DRIVE and press Return. From here on I will refer to your formatted disk as 'Empty' which is what the Workbench will call it. The MEDAlloc bootblock works much the same as the MEDAlloc code. However, it is loaded rather differently. What you must do now is to copy MEDRip to Empty by dragging the MEDRip icon to Empty's icon. If you have only one disk drive you will first need to insert Empty and open it's icon to to use Empty, first turn off unneeded rives, then reset the computer and run the program/game/deno you want to rip music out of. Then reset again and quickly insert Empty in the internal drive (do NOT wait for the nice picture of a disk). The MEDAlloc bootblock will run just as the MEDAlloc "KickTag' code (described above) does. When it has finished, you will be left with a single window on the screen titled 'AmigaDOS' . How type 'MEDRip' and press Return. MEDRip will load and run as normal. You will have suggest?). lenty of space on Empty to save modules (as its name would This tiny utility just wipes out any modules in memory so that they are invisible to the MEDAlloc 'KickTag' code and bootblock and so won't take up any valuable memory. It will then reboot, freeing all memory and allowing you to restart with all your memory available. It will take a little while before it resets to check all through memory - a maximum of 5 seconds for each megabyte of memory switched on. During this time nothing will seem to be happening - this is normal. WARNING: Before running MEDWipe you should ensure that any data you are working on is saved to disk, and that all disk access has stopped. Otherwise you could lose your work or worse still corrupt a disk! Shell Usage: MEDWipe Workbench usage: Double-click the MEDWipe icon. CKNOWLEDGEMENTS Thanks also to Hico Pratols for peytools.debrart Excellent documentation, which is. like the library itseir, Please write to me if you have any comments, bug reports or programming hints to make. My address (Snail mail only, sorry!) is: Ben Hutchings 43 Harrison Close Reigate
(.png)
